Skip to content

Configure GitHub Discussions with category forms and auto-promotion workflow - #2

Closed
cuongmx with Copilot wants to merge 3 commits into
mainfrom
copilot/setup-github-discussions
Closed

cuongmx with Copilot wants to merge 3 commits into
mainfrom
copilot/setup-github-discussions

Conversation

Copilot AI commented Nov 9, 2025 •

Copy link
Copy Markdown

Implements complete GitHub Discussions setup to centralize community Q&A, feature requests, and documentation feedback per the Vietnamese configuration guide.

Changes

Issue template configuration

  • .github/ISSUE_TEMPLATE/config.yml – Redirects to Discussions categories, disables blank issues

Discussion category forms

  • .github/DISCUSSION_TEMPLATE/{q-a-support,ideas-feedback,docs-feedback,show-and-tell,announcements}.yml – Structured forms with required fields, dropdowns, and validation

Auto-promotion workflow

  • .github/workflows/discussion-promote.yml – Converts Ideas/Feedback discussions to Issues via /promote command, applies triage, from:discussion labels

Documentation

  • .github/DISCUSSIONS_GUIDELINES.md – Community posting standards
  • .github/PINNED_TOPICS.md – Content for 3 pinned welcome/template topics
  • .github/SETUP_SUMMARY.md – Post-merge manual steps (enable feature, create categories, map forms, pin topics)
  • README.md – Added Discussions badge and link in Community section

Post-merge actions required

  1. Settings → Features → Enable Discussions
  2. Create categories: Q&A / Support, Ideas & Feedback, Docs Feedback, Show & Tell, Announcements
  3. Settings → Discussions → Map each .yml form to matching category
  4. Create and pin 3 starter topics from PINNED_TOPICS.md
  5. Test /promote in Ideas category

Detailed instructions in .github/SETUP_SUMMARY.md.

Original prompt

Giúp tôi cấu hình discussion như guide ở dưới:

GitHub Discussions Setup – Ready-to-Paste Config

Copy these files into your repo. After pushing to default branch, enable Discussions in repo settings and map categories to templates.


1) Direct users to Discussions (and provide links)

File: .github/ISSUE_TEMPLATE/config.yml

blank_issues_enabled: false
contact_links:
  - name: 💬 Q&A / Support (GitHub Discussions)
    url: https://github.com/orgs/requestbin/discussions/categories/q-a-support
    about: Ask questions and get help from the community and maintainers.
  - name: 💡 Ideas & Feature Requests (Discussions)
    url: https://github.com/orgs/requestbin/discussions/categories/ideas-feedback
    about: Propose new apps, features, or improvements.
  - name: 📚 Docs Feedback (Discussions)
    url: https://github.com/orgs/requestbin/discussions/categories/docs-feedback
    about: Suggest edits, report gaps, or ask for examples.
  - name: 🚀 Show & Tell / Use cases (Discussions)
    url: https://github.com/orgs/requestbin/discussions/categories/show-and-tell
    about: Share what you built with RequestBin.

2) Discussion category forms (Discussion Templates)

Place the following files in .github/DISCUSSION_TEMPLATE/.

These create forms when users start a new discussion inside a category. After pushing, go to Settings → Discussions → Category forms and map each template to the matching category.

2.1) Q&A / Support

File: .github/DISCUSSION_TEMPLATE/q-a-support.yml

labels: ["discussion: q&a"]
category: Q&A / Support
---
body:
  - type: markdown
    attributes:
      value: |
        Thanks for opening a Q&A! Please provide enough detail so others can help.
  - type: input
    id: topic
    attributes:
      label: Topic summary
      description: One sentence describing the question.
      placeholder: e.g., How to inspect SMTP callbacks?
    validations:
      required: true
  - type: textarea
    id: details
    attributes:
      label: Details
      description: Steps tried, expected vs actual, screenshots, etc.
    validations:
      required: true
  - type: dropdown
    id: area
    attributes:
      label: Area
      options:
        - App Hub / Apps
        - Inspect / Bin
        - Docs
        - Other
  - type: input
    id: links
    attributes:
      label: Links
      description: Optional links (bin URL without secrets, docs page, etc.)

2.2) Ideas & Feedback

File: .github/DISCUSSION_TEMPLATE/ideas-feedback.yml

labels: ["discussion: idea"]
category: Ideas & Feedback
---
body:
  - type: markdown
    attributes:
      value: |
        Share your idea! High-signal posts are easier to prioritize.
  - type: input
    id: what
    attributes:
      label: What would you like to build or improve?
      placeholder: New App – DNS Callback Inspector
    validations:
      required: true
  - type: textarea
    id: problem
    attributes:
      label: Problem / use case
      description: What problem does this solve? Who benefits?
    validations:
      required: true
  - type: textarea
    id: proposal
    attributes:
      label: Proposal / rough design
      description: Sketch the UI flow or APIs if relevant.
  - type: checkboxes
    id: scope
    attributes:
      label: Scope
      options:
        - label: App page
        - label: Bin integration
        - label: Docs update
        - label: SDK/API

2.3) Docs Feedback

File: .github/DISCUSSION_TEMPLATE/docs-feedback.yml

labels: ["discussion: docs"]
category: Docs Feedback
---
body:
  - type: markdown
    attributes:
      value: |
        Help us improve the docs. Please include the page link.
  - type: input
    id: page
    attributes:
      label: Docs page URL
      placeholder: https://requestbin.net/docs/... or /apps/.../docs
    validations:
      required: true
  - type: textarea
    id: issue
    attributes:
      label: What's missing or unclear?
    validations:
      required: true
  - type: textarea
    id: suggestion
    attributes:
      label: Your suggested fix or example

2.4) Show & Tell

File: .github/DISCUSSION_TEMPLATE/show-and-tell.yml

labels: ["discussion: show"]
category: Show & Tell / Use cases
---
body:
  - type: markdown
    attributes:
      value: |
        Share what you built with RequestBin! Links and screenshots welcome.
  - type: input
    id: title
    attributes:
      label: Project title
      placeholder: Slack bot using RequestBin Apps
      validations:
        required: true
  - type: textarea
    id: description
    attributes:
      label: Description & links
      description: Repo/demo link, what it does, and how RequestBin helped.
      validations:
        required: true

2.5) Announcements (maintainers only)

File: .github/DISCUSSION_TEMPLATE/announcements.yml

labels: ["announcement"]
category: Announcements
---
body:
  - type: markdown
    ...

</details>



<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

Copilot AI and others added 2 commits November 9, 2025 09:30
Co-authored-by: cuongmx <10446854+cuongmx@users.noreply.github.com>
Co-authored-by: cuongmx <10446854+cuongmx@users.noreply.github.com>
Copilot AI changed the title [WIP] Add GitHub Discussions setup configuration Configure GitHub Discussions with category forms and auto-promotion workflow Nov 9, 2025
Copilot AI requested a review from cuongmx November 9, 2025 09:35
@cuongmx cuongmx closed this Nov 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants